Fix debug session to be deleted in $sessionDidDestroy instead of $terminateDebugSession #10954
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What it does
Related to #10953.
Cause
$terminateDebugSession
always comes before$sessionDidDestroy
and removes debug session fromsessions
.As a result,
$sessionDidDestroy
never firesonDidTerminateDebugSessionEmitter
, because there is no session at the moment of the execution.Solution
$terminateDebugSession
shouldn't delete debug session, it should only terminate (stop) it - it comes from the method name.$sessionDidDestroy
should delete debug session - it also comes from the method name.How to test
Expected behavior
Review checklist
Reminder for reviewers